Skip to content

Conversation

@Vortexxito
Copy link

Version
Minecraft Neoforge 1.21.1

Description

This PR fixes a critical issue causing severe console spam and TPS drops during world generation, specifically related to the Pillager structures.

The Issue
When generating chunks containing this structure, the server console is flooded with the following error: [Worker-Main-1/WARN] [minecraft/JigsawPlacement]: Empty or non-existent pool: structory:harvest/well_bottoms

This causes significant lag (TPS drops) and slows down pre-generation tools like Chunky, as the game fails to locate the requested template pool.

The Cause
This file was named without the .json

The Fix
Just had to add the .json in the name of the file and the error disappears. This successfully resolves the "non-existent pool" error, stops the console spam, and restores normal world generation performance.

**Description**
This PR fixes a critical issue causing severe console spam and TPS drops during world generation, specifically related to the Pillager structures.

**The Issue**
When generating chunks containing this structure, the server console is flooded with the following error:
`[Worker-Main-1/WARN] [minecraft/JigsawPlacement]: Empty or non-existent pool: structory:harvest/well_bottoms`

This causes significant lag (TPS drops) and slows down pre-generation tools like Chunky, as the game fails to locate the requested template pool.

**The Cause**
This file was named without the .json

**The Fix**
Just had to add the .json in the name of the file and the error disappears.
This successfully resolves the "non-existent pool" error, stops the console spam, and restores normal world generation performance.
@catter1
Copy link
Contributor

catter1 commented Jan 9, 2026

I'll look into it for the next version. This is one of those bugs where some variation of it has existed for several years, and every time I "fix" it I somehow accidentally break something else.

I should note, due to the way our Github repos are set up, I will be closing the PR instead of merging, and be manually making the changes in our dev repo.

Inconsequential side note: are you certain it's causing significant lag? That surprises me, I would expect the game to search for the file, not find it, spit out an error, and continue. An extra step or two, but it should not dramatically slow down Chunky, it's not like this happens multiple times per chunk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants